fix : corrected auth context API paths, action parameter, and user session fetch - #3
Open
tmdeveloper007 wants to merge 1 commit into
Open
Conversation
…user fetch
- Change API base to use empty string fallback so relative /api/auth paths work in browser
- Fix signup and login to call /api/auth (was /auth/signup and /auth/login — wrong paths)
- Add action parameter ('signup'/'login') required by backend API route
- Add captchaToken parameter to signup and login calls
- Replace non-existent /auth/me fetch with supabase.auth.getSession() for user session restore
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes (upstream issues disabled — no issue created).
Summary of What Has Been Done:
Fixed three correctness bugs in app/contexts/AuthContext.js: (1) signup() and login() called the API at /auth/signup and /auth/login instead of the correct /api/auth path; (2) both functions omitted the required action and captchaToken parameters that the backend /api/auth route expects, causing all calls to fail with 'Invalid action' or 'Captcha token missing'; (3) the fetchUser() useEffect called a non-existent /auth/me endpoint instead of using Supabase's built-in getSession().
Changes Made:
Impact it Made:
Note: Please assign this PR to the
tmdeveloper007account.